Femtocell local breakout mechanisms

ABSTRACT

Local breakout mechanisms can be performed by a femto access point (FAP) to facilitate efficient utilization of backhaul and/or macro networks. In particular, a slave Gateway GPRS Support Node (GGSN) can be integrated within the FAP to directly route the incoming traffic from a user equipment (UE) at the FAP. In one example, Internet bound traffic can be directly routed to the Internet, without employing macro network resources. Further, the system can avoid hairpinning by routing traffic between the UE and a home Local Area Network (LAN) by a anchoring a call or a session in the slave GGSN and facilitate integration of UEs with home applications by employing a UE Digital Home Agent. In addition, the FAP can perform UE-to-UE CS media breakout to facilitate communication between UEs attached to the FAP, without routing the traffic through the core macro network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims the benefit ofpriority to each of, U.S. patent application Ser. No. 12/623,176, filedon Nov. 20, 2009 and entitled “FEMTOCELL LOCAL BREAKOUT MECHANISMS,”which claims the benefit of U.S. Provisional Patent Application No.61/117,005, filed on Nov. 21, 2008, and entitled “FEMTO CELL LOCALBREAKOUT MECHANISMS” and is related to co-pending U.S. patentapplication Ser. No. 12/623,210, filed on Nov. 20, 2009, entitled “HOMESERVICE INTEGRATION AND MANAGEMENT BY EMPLOYING LOCAL BREAKOUTMECHANISMS IN A FEMTOCELL,” co-pending U.S. patent application Ser. No.12/623,223, filed on Nov. 20, 2009, entitled “ SERVICE CONTINUITY DURINGLOCAL BREAKOUT IN A FEMTOCELL,” and co-pending U.S. patent applicationSer. No. 12/623,237, filed on Nov. 20, 2009, entitled “FEMTOCELL LOCALBREAKOUT MANAGEMENT SERVICES”. The entireties of each of the foregoingapplications are incorporated herein by reference.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, moreparticularly, to employing local breakout mechanisms at a femto accesspoint.

BACKGROUND

Femtocells—building-based wireless access points interfaced with a wiredbroadband network—are traditionally deployed to improve indoor wirelesscoverage, and to offload traffic from a mobility radio access network(RAN) operated by a wireless service provider. Improved indoor coverageincludes stronger signal, increased bandwidth, and improved reception(e.g., video, sound, or data), ease of session or call initiation, andsession or call retention, as well. Offloading traffic from a RANreduces operational and transport costs for the service provider since alesser number of end users consumes macro RAN over-the-air radioresources (e.g., radio traffic channels), which are typically limited.With the rapid increase in utilization of communications networks and/ordevices, mobile data communications have been continually evolving dueto increasing requirements of workforce mobility, and, services providedby femtocells can be extended beyond indoor coverage enhancement.

Conventional systems that employ femtocells, transport information(e.g., data and/or voice) from a user equipment (UE) including Internetbound traffic through a landline network to a mobility core network. Theinformation is received at the mobility core network and the Internetbound data can be identified and routed to the Internet from the corenetwork. This hairpin type of traffic routing can lead to significantnetwork resource utilization and can cause congestion in the landlinenetwork and/or mobility core network. Further, since data sent by the UEis routed to the Internet from the mobility core network only aftertraversing through the landline network, the response time issubstantially high.

Traditional femtocells transport UE traffic to the mobile serviceprovider network (e.g., core network) via a home broadband service(Digital subscriber line (DSL), Cable, Fiber, etc.). During UE-to-UEcommunication, the traffic is directed from one UE to another via thecore network, even when both the UEs are attached to the femtocell.Accordingly, bandwidth utilization in the traditional approach isinefficient and can negatively impact performance and customersatisfaction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system that facilitates efficientutilization of network bandwidth during wireless communication in afemtocell.

FIG. 2 illustrates an example system that can be employed to facilitatelocal breakout mechanisms that efficiently utilize network bandwidthand/or resources associated with a backhaul pipe and/or a macro RAN.

FIG. 3 illustrates an example system that can be employed to facilitateefficient routing of traffic within a femtocell.

FIG. 4 illustrates an example a Digital Home (DH) femtocell architecturewherein a residential gateway (RG) can be externally connected to afemto access point (AP).

FIG. 5 illustrates an example system that facilitates user equipment(UE)-to-UE circuit switched (CS) media breakout within a femtocell.

FIG. 6 illustrates an example system that provides home servicesintegration with a femtocell, according to an aspect of the subjectdisclosure.

FIG. 7 illustrates an example system that facilitates automating one ormore features in accordance with the subject innovation.

FIG. 8 illustrates an example methodology that can efficiently utilizebackhaul network bandwidth and macro network resources.

FIG. 9 illustrates an example methodology that facilitates localbreakout at a femto AP.

FIG. 10 illustrates an example methodology that facilitates homeapplication integration with a femto AP in accordance with an aspect ofthe subject disclosure.

FIG. 11 illustrates an example methodology that facilitates UE-to-UE CSmedia breakout, according to an aspect of the subject disclosure.

FIG. 12 illustrates an example wireless communication environment withassociated components for operation of a femtocell in accordance withthe subject specification.

FIG. 13 illustrates a schematic deployment of a macro cell and afemtocell for wireless coverage in accordance with aspects of thedisclosure.

FIG. 14 illustrates an example embodiment of a femto access point thatcan facilitate local breakout, according to the subject disclosure.

FIG. 15 illustrates a block diagram of a UE suitable for communicationwith a DH LAN via a femto network in accordance with the innovation.

FIG. 16 illustrates a block diagram of a computer operable to executethe disclosed communication architecture.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It may be evident,however, that the various embodiments can be practiced without thesespecific details, e.g., without applying to any particular networkedenvironment or standard. In other instances, well-known structures anddevices are shown in block diagram form in order to facilitatedescribing the embodiments in additional detail.

As used in this application, the terms “component,” “module,” “system,”“interface,” “platform,” “service,” “framework,” “connector,” “agent,”or the like are generally intended to refer to a computer-relatedentity, either hardware, a combination of hardware and software,software, or software in execution or an entity related to anoperational machine with one or more specific functionalities. Forexample, a component may be, but is not limited to being, a processrunning on a processor, a processor, an object, an executable, a threadof execution, a program, and/or a computer. By way of illustration, bothan application running on a controller and the controller can be acomponent. One or more components may reside within a process and/orthread of execution and a component may be localized on one computerand/or distributed between two or more computers. As another example, aninterface can include I/O components as well as associated processor,application, and/or API components.

Further, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, and flash memory devices (e.g., card, stick, key drive . .. ). Additionally it should be appreciated that a carrier wave can beemployed to carry computer-readable electronic data such as those usedin transmitting and receiving electronic mail or in accessing a networksuch as the Internet or a local area network (LAN). Of course, thoseskilled in the art will recognize many modifications can be made to thisconfiguration without departing from the scope or spirit of the variousembodiments.

In addition, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”subscriber station,” “access terminal,” “terminal,” “handset,” “mobiledevice,” and similar terminology, refer to a wireless device utilized bya subscriber or user of a wireless communication service to receive orconvey data, control, voice, video, sound, gaming, or substantially anydata-stream or signaling-stream. The foregoing terms are utilizedinterchangeably in the subject specification and related drawings.Likewise, the terms “access point,” “base station,” “Node B,” “evolvedNode B,” “home Node B (HNB),” and the like, are utilized interchangeablyin the subject application, and refer to a wireless network component orappliance that serves and receives data, control, voice, video, sound,gaming, or substantially any data-stream or signaling-stream from a setof subscriber stations. Data and signaling streams can be packetized orframe-based flows. Additionally, the terms “femtocell network”, and“femto network” are utilized interchangeably, while “macro cell network”and “macro network” are utilized interchangeably herein. Further, theterms “core network”, “mobility core network”, “mobile core network”,“core mobility network”, “core mobile network” and “mobility network”are utilized interchangeably herein.

Furthermore, the terms “user,” “subscriber,” “customer,” and the likeare employed interchangeably throughout the subject specification,unless context warrants particular distinction(s) among the terms. Itshould be appreciated that such terms can refer to human entities orautomated components supported through artificial intelligence (e.g., acapacity to make inference based on complex mathematical formalisms),which can provide simulated vision, sound recognition and so forth. Inaddition, the terms “femtocell access point”, “femtocell” and “femtoaccess point” are also utilized interchangeably.

Systems and methods disclosed herein employ local breakout mechanisms ata femto access point (AP) that can reduce network congestion in a macroRAN and/or a backhaul network connected to the femto AP. In one aspect,a local broadband network (e.g., Digital Subscriber Line network) canfacilitate access to the Internet and accordingly the Internet bounddata received at the femto AP can be directly routed to the Internet bybreaking out the traffic at the femto AP. Thus, network congestion onthe backhaul pipe and/or the macro RAN can be significantly reduced.Further, since for example, Internet bound data is not transmittedthrough the core macro network, faster response and improved performancecan be achieved for the end user.

Additionally, the disclosed systems & methods enable a UE, attached to afemtocell, for example, in a home, to initiate direct communication withan application within the home (e.g., on a home network), withouthairpinning the traffic from the femtocell in the home network to thecore network and back to the home network. Similarly, a home basedapplication communicating with the UE, can initiate communication via afemto access point without traffic hairpinning.

The systems and methods disclosed herein, in one aspect thereof, canfacilitate local breakout mechanisms at a femto access point (FAP) toreduce backhaul and/or macro network congestion. Moreover, a slaveGateway GPRS Support Node (GGSN) can be integrated within the FAP todirectly route the incoming traffic from a user equipment (UE) at theFAP. In one example, Internet bound traffic can be directly routed tothe Internet via a Digital home (DH) Local Area Network (LAN). Inanother example, traffic bound to a locally connected UE, can bedirectly routed to the UE from the FAP, without routing the trafficthrough the core macro network.

In accordance with another aspect of the system, a routing component cananalyze the received packet to determine an optimal path for the packetfrom the FAP. Moreover, the routing component can determine adestination address, source address, type of packet, type of protocolassociated with the packet, and/or one or more user defined rules orpolicies and/or user preferences, etc. Based in part on the determinedinformation, the routing component can compute the optimal path totransfer the received packet, such that, network bandwidth isefficiently utilized. In one aspect, the routing component can determinean optimal route for a received packet by employing load-balancingtechniques, to avoid network congestion. Additionally or alternately,the routing component can employ one or more machine learning techniquesto facilitate efficient network and/or resource utilization. Further,the routing component can also perform a cost-benefit analysis todetermine an optimal route associated with minimal billing charges.

Yet another aspect of the disclosed subject matter relates to a methodthat can be employed to facilitate local breakout mechanisms at a FAP toimprove network performance and response times. The method comprisesreceiving a packet at the FAP, from a UE. Further, an analysis isperformed on the received packet to determine information associatedwith routing of the packet (e.g., source address, destination address,etc.). Furthermore, a route can be determined for transferring thepacket from the FAP based in part on the analysis, PolicyDecision/Policy Enforcement Functions (PDF/PEF) specified by a serviceprovider, user defined rules or policies, and/or user preferences.Accordingly, the packet can be routed via the determined route.

Aspects, features, or advantages of the subject innovation can beexploited in substantially any wireless communication technology; e.g.,Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), EnhancedGeneral Packet Radio Service (Enhanced GPRS), Third GenerationPartnership Project (3GPP) Long Term Evolution (LTE), Third GenerationPartnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB), High SpeedPacket Access (HSPA), or Zigbee. Additionally, substantially all aspectsof the subject innovation can be exploited in legacy telecommunicationtechnologies.

Referring initially to FIG. 1, there illustrated is an example system100 that facilitates efficient utilization of network bandwidth duringwireless communication in a femtocell, according to an aspect of thesubject disclosure. In one embodiment, a user equipment (UE) 102, can belocated within a coverage area of a femto access point (FAP) 104 and canattach to the FAP 104 by employing most any attachment procedure.Typically, the UE 102 as disclosed herein can include most anycommunication device employed by a subscriber, such as, but not limitedto, a cellular phone, a personal digital assistant (PDA), a laptop, apersonal computer, a media player, a gaming console, and the like.Moreover, the UE 102 can access the mobile core network 109 throughfemto network via FAP 104 and/or via base station 106. It can beappreciated that the macro core network 109 can include most any radioenvironment, such as, but not limited to, Universal MobileTelecommunications System (UMTS), Global System for Mobilecommunications (GSM), LTE, WiMAX, CDMA, etc. The signaling and bearertechnologies, for example circuit switched (CS), and/or packet switched(PS), in a femtocell and macro cell can be the same or different,depending on the radio technologies involved.

Typically, traffic flows between the FAP 104 and mobile core network 109and/or between the base station 106 and mobile core network 109 througha broadband backhaul 110 (e.g., optical fiber based technologies (e.g.,Ethernet, DS3, etc.), twisted-pair line based technologies (e.g., DSL,T1/E1 phone line, etc.), or coaxial cable based technologies (e.g.,DOCSIS, etc.). The FAP 104 generally can rely on the broadband backhaul110 for signaling, routing and paging, and for packet communication.According to an embodiment, the FAP 104 can include a routing component108 that can be utilized to facilitate efficient management of trafficto and/or from the FAP 104.

In one example, the routing component 108 can include a slave GatewayGPRS Support Node (GGSN). Typically, the slave GGSN can implement asubset of functionality implemented by a GGSN in the core network 109.For example, a routing functionality can be implemented by the slaveGGSN to perform local breakout at the FAP 104. In addition, the slaveGGSN can enable anchoring of a communication session at the routingcomponent 108 rather than the core network GGSN. In one aspect, therouting component 108 can receive traffic (e.g., voice, data, media,etc.) from the UE 102 and/or from the base station 106 (e.g., via thebroadband backhaul 110), analyze the received information and determinea route for the received traffic. According to one embodiment, therouting component 108 can selectively route UE traffic away from an Iuhtunnel and send the traffic to a residential/enterprise local IP networkdestination, for example, via a home network, Local Area Network (LAN),and/or a broadband access network (e.g., Internet) (not shown).

For example, the routing component can receive communication packetssent by UE 102 connected to the FAP 104 and can determine informationassociated with the received packet that can facilitate routing of thepacket from the FAP 104 via the slave GGSN. As an example, the routingcomponent 108 can check a header associated with the received packet anddetermine a destination address. Based in part on the determineddestination address, the routing component 108 can compute an optimalroute to transfer the received packet, such that, network bandwidth isefficiently utilized. Moreover, the routing component 108 can facilitateroute determination based in part on a destination address, sourceaddress, type of packet, type of protocol, one or more user and/orservice provider defined rules or policies and/or user preferences.Additionally, the routing component 108 can utilize load balancingmechanisms, machine learning techniques, and/or a cost benefit analysisto generate a route for the received packets.

Typically, a femto gateway (not shown) can aggregate regional trafficreceived from multiple FAPs and tunnel the traffic to the core network109. The conventional circuit switched (CS) traffic can be routed to aMobile Switching Center (MSC) and the packet switched (PS) traffic canbe routed to a Serving GPRS Support Node (SGSN) and Gateway GPRS SupportNode (GGSN). According to an aspect, the routing component 108 canfacilitate communication between UE 102 and a device on a home network(not shown) by directly routing information between the UE 102 and thehome network (e.g., without routing the traffic through the core network109). Accordingly, the UE 102 can communicate with the home device overa home LAN when UE 102 is attached to the FAP 104. It can be appreciatedthat when UE 102 detaches from the FAP 104, the core network 109 canmaintain a connection to the UE 102 via the mobility network (e.g.,through base station 106). Similarly, routing component 108 can routeInternet bound traffic, received from the UE 102, directly to theInternet, for example, via the home LAN.

In particular, the routing component 108 can examine traffic sourced inthe UE 102 to separate home bound, broadband access network bound and/orInternet bound traffic from the rest. A network address translation(NAT) can be performed to proxy the Internet Protocol (IP) address of UE102 assigned by mobile core with a home network domain IP address. Therouting component 108 can then send the IP traffic over the home LAN.Similarly, the routing component 108 can examine traffic that sources inthe home network and is destined to the UE 102. A NAT can be performedto proxy the home domain IP address with the IP address of the UE 102.Accordingly, the routing component 108 can deliver the traffic from thehome LAN to the UE 102.

Additionally, routing component 108 can achieve UE-to-UE CS breakouttraffic. Moreover, the routing component 108 can facilitate directlyrouting communication between two or more UEs connected to the FAP 104,without utilizing the broadband backhaul 110. The routing performed atthe FAP 104 can substantially save network capital investments, time andresources through lowered duplicity and/or increment of the networkinfrastructure. Further, the quality on customer applications can beimproved and a faster response time can be achieved.

FIG. 2 illustrates an example system 200 that can be employed tofacilitate local breakout mechanisms that efficiently utilize networkbandwidth and/or resources associated with a backhaul pipe and/or amacro RAN, in accordance with an aspect of the disclosure. It can beappreciated that the routing component 108 can include functionality, asmore fully described herein, for example, with regard to system 100.

In one aspect, the system 200 comprises a routing component 108, whichcan typically include a packet receiving component 202 that can beemployed to receive information, such as, but not limited to data,voice, media, control data and/or a combination thereof, from a UE andFemto Gateway. Typically, the UE can include most any electronic devicethat can connect wirelessly to a FAP 104, such as, but not limited to,mobile phones, media players, digital cameras, media recorders, laptops,PDAs (personal digital assistants), personal computers, printers,scanners, digital photo frames, GPS module, gaming module, etc. Further,it can be appreciated the UE can be mobile, stationary, and/or havelimited mobility and can employed, for example, in a home, office,building, retail store, restaurant, hotel, factory, warehouse, etc.

In one aspect, the packet receiving component 202 can be employed toreceive communication packets sent by one of the multiple registered UEsconnected to the femto AP. Additionally, packet receiving component 202can receive communication packets, through a home/enterprise networkand/or macro network. Specifically, the femtocell can be connected tothe home/enterprise network by most any registration process. Accordingto an embodiment, a packet inspection component 204 can be employed toanalyze information associated with the received packet to facilitaterouting of the packet from the femto AP. In one aspect, the packetinspection component 204 can determine a destination address associatedwith the received packet, for example, by checking an IP headerassociated with the received packet. Accordingly, the packet inspectioncomponent 204 can generate an optimal route to transfer the receivedpacket, based in part on the determined destination address, such that,network bandwidth is efficiently utilized.

It can be appreciated that the packet inspection component 204 canemploy most any analysis technique to determine routing of a receivedpacket, such as, but not limited to, routing based in part on adestination address, source address, type of packet, type of protocol,one or more user and/or service provider defined rules or policiesand/or user preferences. According to an example, the packet inspectioncomponent 204 can determine an optimal route for a received packet, toavoid network congestion. Additionally or alternately, the packetinspection component 204 can employ load-balancing techniques tofacilitate efficient network and/or resource utilization. In one aspect,the packet inspection component 204 can utilize one or more machinelearning techniques to facilitate automating one or more features inaccordance with the subject innovation, as discussed in detail infrawith respect to FIG. 7.

The routing component 108 can further include a packet routing component206 that can be employed to route a received packet based on the routedetermined by the packet inspection component 204. Moreover, the routingcan include, routing PS traffic between UEs attached to the femtocell,between a UE and a home device, between a UE and the Internet via thehome network, between a UE and the macro network, and/or between a homedevice and the macro network via a backhaul network. It can beappreciated that a NAT can be performed when routing the packets fromone network to another.

Referring now to FIG. 3, there illustrated is an example system 300 thatcan be employed to facilitate efficient routing of traffic within afemtocell, according to an aspect of the subject disclosure. It can beappreciated that the UE 102, FAP 104, and routing component 108 caninclude respective functionality, as more fully described herein, forexample, with regard to systems 100 and 200. Moreover, system 300includes a FAP 104 that can be integrated with an integrated residentialgateway (RG). Further, FAP 104 can be connected to a LAN, for exampledigital home (DH) LAN 310, by a wireless and/or wired connection. It canbe appreciated that the DH LAN 310 disclosed herein, can be most any LANand can be deployed in most any area, such as but not limited to, ahouse, an office, a building, a warehouse, a store, a restaurant, ahotel, a factory, etc.

Typically, the FAP 104 can receive communications from a UE 102. The UE102 can be most any communication device employed by a user, forexample, a cellular phone, a gaming module, a television, a projector,personal computer, etc. Moreover, the UE 102 can utilize varioustechnologies for terrestrial wireless communication, for example, anadvanced second generation (2.5G) telecommunication technology such asEnhanced Data Rate for Global System for Mobile Communications (GSM)Evolution (EDGE); a third generation technology (3G) like ThirdGeneration Partnership Project (3GPP) Universal Mobile TelecommunicationSystem (UMTS), a 3GPP2 Evolution Data Only (EVDO) system, 3GPP Long TennEvolution (LTE), or Ultra-broadband Mobility (UMB); advanced 3G such asWorldwide Interoperability for Microwave Access (WiMax); or a fourthgeneration (4G) technology such as for example Long Tenn Evolution (LTE)Advanced. Additionally, a UE 102 can consume satellite-based trafficsuch as data originated from GPS, GLONNAS, or Galileo systems, conveyedthrough a deepspace link (not shown).

In one aspect, the Home Node B (HNB) 302 can receive communication fromthe UE 102 and can perform Node-B radio functions such as, but notlimited to scheduling. Further, a partial Radio network control (RNC)304 can be employed to perform Radio Resource Control (RRC), radiobearer (RB)/radio access bearers (RABs), radio access network (RAN)quality of service (QoS), call admission control (CAC)/Power/Congestioncontrol, and the like. In accordance with an aspect, a routing component108 can (e.g., by employing a packet inspection component 204) locallybreak out Internet and/or Home Network bound traffic. In one aspect, therouting component 108 can include a slave GGSN. Moreover, informationpackets received from the UE 102 can be analyzed by the routingcomponent 108 and a route to transfer the packets can be determined(e.g., by employing a packet inspection component 204). In one example,the routing can be based in part on a destination address, sourceaddress, type of packet, type of protocol, one or more user and/orservice provider defined rules or policies and/or user preferences.

According to an embodiment, a Policy Decision/Policy EnforcementFunction (PDF/PEF) 306 can be employed to drive the selection of theroute. The PDF/PEF 306 can include multiple policies that can bespecified, for example, by a service provider through a managementcomponent 308. The management component 308 can be employed tofacilitate FAP management (FAP white list, policy rule updates,Ethernet/IP port management, FAP firmware updates, GSN routing functionmanagement, performance and alarm status update etc.). Additionally, themanagement component 308 can employ Technical Report 069 (TR-69)protocol to communicate with a Femto provisioning/management platform inthe mobility network. According to an aspect, when a customer installsthe FAP 104, during setup (or at any other time), the managementcomponent 308 can facilitate authentication of the FAP 104 with themobility network, such that, the service provider can recognize the FAP104 and can ensure that the customer and/or the FAP 104 is legitimate.Further, once the customer and/or FAP 104 are authenticated, themanagement component 308 can download configuration information (e.g.,service provider policies, rules, definitions) and parameters that canfacilitate connection with the core network elements (e.g., GGSN).

In one embodiment, the management component 308 can provide an interfacethat enables a mobility network operator/service provider/mobilitynetwork element to control the local breakout mechanism, for example, byspecifying policies in the PDF/PEF. In one example, the managementcomponent 308 can also provide mobility network operator/serviceprovider/mobility network element with an override functionality.Moreover, the mobility network operator/service provider/mobilitynetwork element can utilize the override functionality to stop localbreakout at most any time and/or for a specified time period.Specifically, the override functionality can be employed by a serviceprovide upon legal request and/or for security purposes. For example, alegal/security request can be made (e.g., by a government agency) tomonitor communication through a particular FAP and the service providercan utilize the management component 308 to override the breakoutmechanisms employed at the FAP, such that all communication at the FAPcan be transferred via the mobility network. Moreover, the managementcomponent 308, in response to the override command, can disable breakoutfunctionality at the routing component 108 and/or create a policy, whichensures that local breakout is not performed at the FAP 104.

The routing component 108, based in part on factors, such as but notlimited to, the analysis, the PDF/PEF, etc., identifies an optimal routefor traffic received at the FAP 104. In one example, when traffic isreceived from the UE 102, the routing component 108 can identify whetherthe traffic should be routed to the macro network, via the Iu tunnel, tothe Internet via the DH LAN 310, a device on the DH LAN 310 and/or adisparate UE (not shown) attached to the FAP 104. Based on thedetermination, the routing component can deliver the traffic via theidentified route. In another example, the routing component 108 canreceive traffic from the device on the DH LAN 310 and can determine anoptimal route (e.g., to UE 102, or macro network, etc.) for the traffic,for example, by employing one or more policies in the PDF/PEF 306, androute the traffic via the optimal route.

Additionally or alternately, a Network address translation(NAT)/Firewall component 312 (e.g., IPv4) can be employed to modifynetwork address information in packet headers that can be routed via thebackhaul network and/or the home network. Typically, the RG canprovision the femtocell with an IP address when the femtocell attachesto the home network, for example DH LAN 310. When the routing component108 determines that the traffic (e.g., from UE 102) can be routed to theDH LAN 310, the NAT/Firewall component 312 can employ a NAT function toreplace the IP address of UE 102 in a packet header, with a home networkdomain IP address associated with the DH LAN 310. Similarly, when therouting component 108 determines that the traffic (e.g., from DH LAN310) can be routed to the UE 102, the NAT/Firewall component 312 canutilize a NAT function to replace the home domain IP address with the IPaddress of the UE 102.

Further, the NAT/Firewall component 312 can employ a firewall forintrusion detection and/or prevention for UE 102 to home/enterprisenetwork traffic and vice versa. Furthermore, the firewall can allow orprevent a device on the DH LAN 310 to access the mobility networkthrough the Iuh tunnel. In one aspect, the NAT/firewall component 312can utilize one or more policies from the PDF/PEF 306 to control accessof the mobility network by the device on the DH LAN 310. For example,the firewall can protect the digital home network and prohibit bridgingthe DH LAN 310 with the Internet through the mobility core network. Itcan be appreciated that the firewall can be hardware, software, or acombination thereof. In one example, a modem 314 (a DSL or most anybroadband modem) can be employed for transmission of packets through thebackhaul network to the macro RAN. Furthermore, the FAP 104 can includea security component 316 that can utilize most any encryption techniquefor secure channel set up and/or tear down and/or encryption of outboundtraffic. For example, the security component can perform encryption forestablishing the Iu tunnel.

Referring to FIG. 4, there illustrated is an example a DH femtocellarchitecture 400 wherein a RG 402 is externally connected to a FAP 104,according to an aspect of the subject specification. It can beappreciated that the routing component 108, UE 102, HNB 302, Partial RNC304, PDF/PEF 306, management component 308, security component 316, DHLAN 310, modem 314, and FAP 104 can include functionality, as more fullydescribed herein, for example, with regard to system 100, 200 and 300.Typically, the RG 402 can be integrated within the FAP 104, as shown inFIG. 3 or can be externally connected to the FAP 104, as shown in FIG. 4according to an aspect of the subject disclosure. However, it can beappreciated that the working and implementation of systems 300 and 400can be substantially similar.

As discussed previously, the routing component can route traffic betweenUE 102 and the DH LAN 310, UE 102 and the Internet via DH LAN 310, UE102 and a disparate UE attached to the FAP 104, and/or UE 102 and themacro network. According to an aspect, a NAT/Firewall component 312 _(a)can be employed to facilitate network address mapping for information inpacket headers that are routed via the backhaul network and/or the homenetwork. Typically, the NAT/Firewall component 312 _(a) can employ a NATfunction to replace the IP address of UE 102 in a packet header with ahome network domain IP address associated with the DH LAN 310.Similarly, when the routing component 108 determines that the traffic(e.g., from DH LAN 310) can be routed to the UE 102, the NAT/Firewallcomponent 312 _(a) can employ a NAT function to replace the home domainIP address with the IP address of the UE 102. Further, the NAT/Firewallcomponent 312 _(b) can employ a firewall for intrusion detection and/orprevention. For example, the firewall can prevent bridging the DH LAN310 with the Internet through the mobility core network. It can beappreciated that the firewall can be hardware, software, or acombination thereof. In one aspect, a RG 402 can be utilized to directtraffic to the mobility network through the backhaul network backbone.

Referring to FIG. 5, there illustrated is an example system 500 thatfacilitates UE-to-UE CS media breakout within a femtocell in accordancewith an aspect of the subject disclosure. It can be appreciated that therouting component 108, management component 308 and FAP 104 can includefunctionality, as more fully described herein, for example, with regardto system 100, 200, 300 and 400.

One or more UEs (502, 504) can attach to the FAP 104 when the UEs (502,504) are within the coverage area of the FAP 104, for example, byemploying most any attachment procedure. It can be appreciated that theFAP 104 can utilize an authentication and/or authorization technique toprevent unauthorized attachments. For example, the FAP 104 can manageaccess to femtocell services through access control list(s) 508, e.g.,white list(s) or black list(s). Such access control list(s) 508 can beconfigured through various apparatuses and in various modes, e.g.,interactively or automatically, which facilitates access management ofaccess to femtocell coverage. As an example, white list(s) includes aset of UE(s) identifier numbers, codes or tokens, and can also includeadditional fields that can contain information respectively associatedwith communication devices to facilitate femtocell access managementbased at least in part on desired complexity; for example, an additionalfield in a white list can be a logic parameter that determines whetheran associated identifier is available for dissemination across disparatewhite lists. Values of attribute fields that determine white list(s),black list(s), or white list profile(s) can be generated through varioussources. The management component 308 can facilitate generation andmaintenance of white list(s), black list(s), or white list profile(s).

In addition, the management component 308 can be employed to create,update and/or delete information that facilitates routing and/orauthentication, which can be stored in database 506. Although database506 is shown to reside within the FAP 104, it can be appreciated thatdatabase 506 can be a local, a remote, and/or a distributed database.The database 506 can be employed to store information such as, but notlimited to, access control list 508, user preferences 510, attached UEparameters 512 and/or service provider policies 514. The serviceprovider policies 514 can typically include one or more policiesassociated with routing and/or breakout at the FAP 104. In addition, theservice provider policies 514 can include the PDF/PEF that can drive theselection of an optimal route, for example, by the routing component108. Further, the attached UE parameters 512 can provide a list ofcurrently attached UEs (502, 504) and can typically include information(e.g., device ID, SIM, USIM, a mobile number, etc.) associated with theUEs (502, 504) that are currently attached to the FAP 104.

In one example, when UE 502 initiates a call, the routing component 108can analyze the CS traffic from the UE 502 and determine an optimal pathto route the call. As an example, the routing component 108 can analyzeinformation stored in the database 506, such as, but not limited to userpreferences 510, attached UE parameters 512 and/or service providerpolicies 514, to determine the optimal path. In one aspect, the routingcomponent 108 can verify whether the destination device for the CS callis attached to the FAP 104, for example, by employing information fromthe attached UE parameters 512. When the routing component 108determines that the destination entity is not attached to the FAP 104,the routing component 108 can direct the call to the macro network viathe backhaul network. Alternately, when the routing component 108determines that the destination entity is attached to the FAP 104, forexample, if the destination entity is UE 504, the routing component 108can facilitate CS media breakout at the FAP 104 and facilitatecommunication between the UE 502 and UE 504 without routing the callthrough the macro network. It can be appreciated that when one of orboth the UEs move out of the femtocell coverage area, service continuitycan be established and the call can be routed via the macro network.Further, it can be appreciated that the routing component can transmitdata indicating the CS media breakout to the core mobility network(e.g., that can be utilized for billing and/or records, etc.)

It can be appreciated that the database 506 can include volatile memoryor nonvolatile memory, or can include both volatile and nonvolatilememory. By way of illustration, and not limitation, nonvolatile memorycan include read only memory (ROM), programmable ROM (PROM),electrically programmable ROM (EPROM), electrically erasable PROM(EEPROM), or flash memory. Volatile memory can include random accessmemory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such asstatic RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), doubledata rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM(SLDRAM), and direct Rambus RAM (DRRAM). The memory (e.g., data stores,databases) of the subject systems and methods is intended to comprise,without being limited to, these and any other suitable types of memory.

FIG. 6 illustrates an example system 600 that provides home servicesintegration with a femtocell, according to an aspect of the subjectdisclosure. Typically, system 600 can include a FAP 104 that cancomprise an integrated (as shown in FIG. 3) or external RG (as shown inFIG. 4). It can be appreciated that the routing component 108,NAT/Firewall component 312, modem 314, security component 316, and FAP104 can include functionality, as more fully described herein, forexample, with regard to system 100, 200, 300, 400 and 500. Additionally,it can be appreciated that FAP 104 can include components (e.g., HNB,partial RNC, management component, PDF/PEF, etc.) as illustrated inFIGS. 3-4 and described herein with respect to systems 300 and 400.

According to an embodiment, the routing component 108 can facilitatecommunication between a UE (602, 604) and one or more devices 606 on theDH LAN 310. Typically, device 606 can be most any device on the DH LAN310, such as, but not limited to, a telephone, a printer, a laptop, anappliance, a television, a projector, a gaming module, music player,etc. Thus, the UE (602, 604) can join the LAN (e.g., home network),without supporting a dual mode wireless/Wi-Fi functionality. Inaddition, the routing component 108 can directly route Internet boundpackets to the Internet, without transferring the packets to the corenetwork. Further, the routing component 108 can identify communicationdirected to a device on the LAN and route the communication directly tothe destination via the DH LAN 310.

According to an embodiment, the FAP 104 can include a UE DH agent 608that can facilitate communication between UE 602 and a device 606 on theDH LAN 310. In one aspect, the UE DH agent 608 can identify when a UE602 attaches to the FAP 104 and can communicate the presence of the UE602 to the DH functions. Similarly, the UE DH agent 608 can identifywhen the UE 602 leaves the femtocell and accordingly communicate theabsence of the UE 602 to the DH functions. Moreover, the UE DH agent 608can perform mapping to provide DH functions to the UE 602. Specifically,the UE DH agent 608 can make the UE 602 appear as a DH compliant devicein the DH LAN 310.

According to one aspect, the UE DH agent 608 can render anapplication-specific User Interface (UI) on a display on the UE 602. Asan example, a user can interact with the displayed UI and communicatewith and/or control the devices on the DH LAN 310. For example, the UEDH agent 608 can render a webpage, which can include information and/orinteractive buttons, which enable the user to monitor and/or controldevices 606. Further, the UE DH agent 608 can provide a coherent UIacross all UEs attached to the FAP 104. Moreover, the UE DH Agent 608can be a DH compliant agent working together with DH application(s) tointerface the UE 602 with various DH functions and services 610. In oneexample, the FAP 104 can instantiate one UE DH Agent 608 for each UE 602that attaches to the FAP 104, except for those which are not authorizedto access DH services. Specifically, a femtocell Access Control List(ACL) can be maintained by the DH Agent 608 (e.g., by employinginformation stored in database 506) to authorize the UE 602 for DHaccess. In an alternate embodiment, the ACL can be maintained by amanagement function (e.g., management component 308) within the FAP 104and accessed by the DH Agent 608, for UE 602 authorization. In oneexample, a UI (e.g., web page) through which the femto AP owner can addand/or delete UE IDs to/from the Femtocell ACL can be provided by the UEDH agent 608. The entries to the ACL can include information, such as,but not limited to, an ID known to the femto AP owner and the user ofthe visiting UE 602 (e.g. telephone number). In one example, the networkprovider can remotely view and/or modify the ACL.

In accordance with an aspect, the UE DH agent 608 can provide anauthorized UE with DH services 610, such as, but not limited to, DigitalRights management (DRM), Remote User Interface (RUI), Dynamic HostConfiguration Protocol (DHCP), session management (SM), Universal Plugand Play (UPnP), Analog Terminal Adapter (ATA). Moreover, the UE DHAgent 608 can offload traffic to the broadband access network. Forexample, UE traffic to/from the Internet can be routed directly to theInternet service provider (ISP) and the DH LAN 310, and can bypass theGSN. Accordingly, the UE DH agent 608 can route signaling and/or mediato and/or from the DH LAN 310 in an efficient manner, avoidinghairpinning (e.g., tromboning). In an additional aspect, the UE DH agent608 can facilitate session continuity for traffic between the UE 602 andselect DH LAN services 610 and/or devices 606, when the UE 602 movesfrom the femtocell to the macro cell and vise versa.

It can be appreciated that the UE DH agent 608 can be located within thefemtocell and/or can be located within a UE, for example the DH client612 in UE 604. In particular, the DH client 612 can includefunctionality substantially similar to that of the UE DH agent 608.Moreover, the DH Client 612 can be a device-specific Digital Homecompliant client, residing in the UE, for delivering DH services to theUE. It can be appreciated that although only one DH client 612 isillustrated in UE 614, one or more DH clients may reside in a UE, eachwith the same or different functionality. In one aspect, the DH Client612 can enhance user experience beyond that which can be provided withthe UE DH Agent 608, for example, based on UE specifications and/or userpreferences.

Further, the FAP 104 can include a femto DH Agent 614 that can beemployed to authenticate the FAP 104 with the home network. For example,the femto DH Agent 614 can facilitate attaching, detaching andestablishing its presence in the DH LAN 310. In addition, the femto DHAgent 614 can facilitate wireline and/or wireless convergence byinter-working between the DH functions 610 and mobile applications 616(e.g., mobility/CARTS functions). For example, the femto DH Agent 614can facilitate location assisted cellular services by obtaining locationof the FAP 104 from a function, application, database, and/or deviceattached to the DH LAN 310 and providing it to the mobility locationservers. Additionally or alternately, the femto DH Agent 614 can assista mobile core charging function for measuring Internet traffic breakoutat the FAP 104. Further, the femto DH Agent 614 can provide trafficbreakout information to a service provider billing system (not shown).

As described previously, the NAT/Firewall component 312 can be employedto modify network address information in packet headers that are routedto/from the UE (602, 604) via the backhaul network and/or the DH LAN310. Further, the NAT/Firewall component 312 can employ a firewall forintrusion detection/prevention and/or for protecting the DH LAN 310 andprohibiting bridging of the DH LAN 310 with the Internet through themobility core network. The security component 316 can encrypt traffic tothe macro RAN to create the Iu tunnel. Further, in one example, a DSLnetwork can be employed, by the FAP 104, as the transport media toconnect to the femto gateway (FGW) 618 located at the edge of themobility core network. The conventional Iu traffic consisting of theCircuit Switched (Iu-cs) voice traffic and Packet Switched (Iu-ps) datatraffic together with Femto signaling can be transported between theFemtocell and Femto Gateway in a secure channel. The Iu over IP protocolcan be referred to as Iu+.

In order to facilitate a fast radio link layer control, functions ofconventional RNC can be split between and integrated into FAP 104 andfemto gateway 618. Functions such as radio bearer management and radioQoS management can be included in the FAP 104 (e.g., by employingpartial RNC 304); and functions of GPRS Tunneling Protocol (GTP) tunnelmanagement, femtocell authentication, mobility management and/orhandover control can be integrated into the FGW 618. In one example, theFGW 618 can aggregate regional femtocells' traffic and tunnel thetraffic to the core network. The conventional circuit switched (CS)traffic is routed to a Mobile Switching Center (MSC) and the packetswitched (PS) traffic is routed to a Serving GPRS Support Node (SGSN)620 and Gateway GPRS Support Node (GGSN) 622.

The UE (602, 604) can activate one or more Packet Data Protocol (PDP)context with the GGSN 622. Typically, up to three PDP contexts can beactive at the same time. The primary PDP Context can be employed forsignaling and best effort traffic. The other two secondary PDP contextscan each be dedicated for data stream with a particular quality ofservice. However, the system 600 can break the PDP context, such that, asubset of functions of the GGSN 622 can be performed by the routingcomponent 108. Accordingly, communication sessions can be anchored atthe routing component 108 instead of core network GGSN 622.

FIG. 7 illustrates an example system 700 that employs an artificialintelligence (AI) component 702, which facilitates automating one ormore features in accordance with the subject innovation. It can beappreciated that the FAP 104 and the routing component 108 can includerespective functionality, as more fully described herein, for example,with regard to systems 100-600.

The subject innovation (e.g., in connection with routing) can employvarious AI-based schemes for carrying out various aspects thereof. Forexample, a process for optimal route determination by the routingcomponent 108 can be facilitated via an automatic classifier system andprocess. Moreover, where the routing component 108 can facilitate localbreakout at the FAP 104, the classifier can be employed to determine howthe received traffic can be routed.

A classifier is a function that maps an input attribute vector, x=(x1,x2, x3, x4, xn), to a confidence that the input belongs to a class, thatis, f(x)=confidence(class). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed. In the case of communicationsystems, for example, attributes can be information within the packetheaders or other data-specific attributes derived from the informationwithin the packet headers, and the classes can be categories or areas ofinterest (e.g., levels of priorities).

A support vector machine (SVM) is an example of a classifier that can beemployed. The SVM operates by finding a hypersurface in the space ofpossible inputs, which the hypersurface attempts to split the triggeringcriteria from the non-triggering events. Intuitively, this makes theclassification correct for testing data that is near, but not identicalto training data. Other directed and undirected model classificationapproaches include, e.g., naïve Bayes, Bayesian networks, decisiontrees, neural networks, fuzzy logic models, and probabilisticclassification models providing different patterns of independence canbe employed. Classification as used herein also is inclusive ofstatistical regression that is utilized to develop models of priority.

As will be readily appreciated from the subject specification, thesubject innovation can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing user behavior, receiving extrinsic information). Forexample, SVM's are configured via a learning or training phase within aclassifier constructor and feature selection module. Thus, theclassifier(s) can be used to automatically learn and perform a number offunctions, including but not limited to determining according to apredetermined criteria whether the received traffic can directly berouted to a home network (e.g., DH LAN 310), whether the receivedtraffic can directly be routed to a disparate UE attached to thefemtocell, whether the received traffic can be routed through the macroRAN, whether the received traffic can directly be routed to Internet,etc. The criteria can include, but is not limited to, the amount oftraffic received, the type of traffic received, the importance (e.g.,priority) of the traffic received, historical patterns, UE behavior,user preferences, service provider preferences and/or policies, femto APparameters, etc.

FIGS. 8-11 illustrate methodologies and/or flow diagrams in accordancewith the disclosed subject matter. For simplicity of explanation, themethodologies are depicted and described as a series of acts. It is tobe understood and appreciated that the subject innovation is not limitedby the acts illustrated and/or by the order of acts, for example actscan occur in various orders and/or concurrently, and with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be required to implement the methodologies in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the methodologies could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be further appreciated that themethodologies disclosed hereinafter and throughout this specificationare capable of being stored on an article of manufacture to facilitatetransporting and transferring such methodologies to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media.

Referring now to FIG. 8, illustrated is an example methodology 800 thatcan efficiently utilize backhaul network bandwidth and macro networkresources in accordance with an aspect of the subject innovation. Inparticular, methodology 800 can facilitate routing of traffic (e.g.,voice, data, media, etc.) at a femto AP and perform local breakout atthe femto AP. In one aspect, the femto AP can be connected to a LAN,such as, but not limited to a DH LAN. At 802, traffic can be received atthe femto AP. For example, the traffic can be received from one or moreUEs attached to the femto AP and/or a device on the LAN, for example,via the LAN.

At 804, the received traffic can be analyzed. In one aspect, adestination address, a source address, type of packet, type of protocolassociated with the traffic can be determined. At 806, additionalinformation associated with the traffic, for example, information storedin a database can be analyzed. The information can include, but is notlimited to, user preferences, UE parameters, femto AP parameters,service provider policies, PDF and/or PEF, etc. At 808, an optimal pathcan be determined to route the traffic based in part on the analysis. Asan example, it can be determined whether local breakout at the femto APis possible and the traffic can be directly routed to its destinationfrom the femto AP, without employing macro network resources. At 810,the traffic can be routed via the optimal path. In one example, trafficfrom a UE can directly be routed to the Internet, without routing thetraffic to the core mobility network.

FIG. 9 illustrates an example methodology 900 that facilitates localbreakout mechanisms at a femto AP, according to an aspect of the subjectdisclosure. In one aspect, an authorized UE located within a coveragearea of a femto access point (FAP) can attach to the FAP by employingmost any attachment procedure. Typically, the UE can include, but is notlimited to, a cellular phone, a personal digital assistant (PDA), alaptop, a personal computer, a media player, a gaming console, and thelike. Once attached to the femto AP, the UE can communicate, forexample, with the macro network via the femto AP. At 902, traffic can bereceived at the femto AP from the UE. It can be appreciated that trafficcan include data, such as, but not limited to, audio, video, multimedia,data, etc. Further, the femto AP can be connected to a LAN, such as ahome network.

At 904, the received traffic along with additional informationassociated with the traffic can be inspected. In one example, adestination address associated with a received packet can be determined,for example, by checking a header of the received packet. Additionallyor alternately, information such as, but not limited to, a sourceaddress, type of packet, type of protocol can also be determined byinspecting the received traffic. Further, a database can be queried todetermine information associated with the received traffic, such as butnot limited to, an ACL, user preferences, attached UE parameters, femtoAP parameters, service provider policies and/or preferences, PDFs and/orPEFs, etc. At 906, it can be determined whether local breakout can beperformed, based in part on an analysis of the determined information.As an example, the determination of performing local breakout can bebased on several additional factors, such as, but not limited to,network congestion control, load-balancing techniques, cost benefitanalysis and/or machine learning techniques.

If determined that local break out cannot be performed, at 910, thetraffic received from the UE can be directed to a macro network (e.g.,core network GGSN) via a backhaul network. Alternately, at 908, thetraffic received from the UE can be directly routed from the femto AP toits destination, when determined that local breakout can be performed.For example, the traffic from the UE can be routed from the femto APdirectly to a disparate UE attached to the femto AP, a device on thehome network, or the Internet.

FIG. 10 illustrates an example methodology 1000 that facilitates homeapplication integration with a femto AP in accordance with an aspect ofthe subject disclosure. The methodology 1000 enables a UE, attached tothe femto AP to communicate with a home device over the home LAN. Incontrast with conventional methodologies wherein traffic from a UE to anapplication within the home, is hairpinned from the home network to theservice provider network and back to the home network, methodology 1000facilitates directly routing traffic received from the UE to the homenetwork, at the femto AP. In one aspect, when the UE leaves thefemtocell, a connection between the UE and the home device can bemaintained by the mobility network.

At 1002, a UE attachment with the femto AP can be identified. In oneexample, this information can be communicated to the home LAN, such thatthe home network services, applications and/or devices are aware of theUEs currently attached to the femto AP. At 1004, UE authorization can bedetermined. In particular, most any authorization and/or authenticationtechniques can be employed to determine whether the UE is authorized toaccess the home LAN. As an example, the service provider and/or thefemto AP owner can create and/or modify a list of authorized user andstore the list at the femto AP. For example, the femto AP owner canrestrict access to the home LAN to UEs associated with family members.At 1006, mapping can be performed to facilitate communication betweenthe authorized UE and a device, service and/or application on the homeLAN. Specifically, the mapping can provide interworking betweendifferent protocols utilized by the UE and by the device, service and/orapplication on the home LAN

In addition, NAT can be employed during communication wherein the UE IPaddress can be replaced with a home LAN domain IP address and IP trafficfrom the UE can be routed to the destination device, service and/orapplication over the home LAN. Similarly, when the traffic sources fromthe device, service and/or application in the home LAN and is destinedto a UE attached to the femto AP, the traffic can be routed to the UEbased on the home domain IP address for the UE, maintained in thefemtocell. Moreover, the home domain IP address can be replaced with theUE IP address and traffic from the home LAN can be routed to the UE.

At 1008, an application-specific UI can be rendered on a display of theUE. As an example, a user can interact with the displayed UI andcommunicate with and/or control the devices on the home LAN. Forexample, a webpage can be rendered in a browser of the UE that can allowa user to monitor, control and/or communicate with a homedevice/application/service. Moreover, the UE can be interfaced withvarious home LAN functions and services, such as but not limited to,Digital Rights Management (DRM), Remote User Interface (RUI), DynamicHost Configuration Protocol (DHCP), session management (SM), UniversalPlug and Play (UPnP), Analog Terminal Adapter (ATA), etc. Further, at1010, the detachment of a UE from the femto AP can be identified.Moreover, this information can be conveyed to the home LAN. In oneaspect, communication between the UE and a device, service and/orapplication on the home LAN can be seamlessly handed over from thefemtocell to the macro cell to provide service continuity.

Referring to FIG. 11, there illustrated is an example methodology 1100that facilitates UE-to-UE CS media breakout, according to an aspect ofthe subject disclosure. At 1102, a call can be received from a UEattached to a femto AP. At 1104, a database can be queried to identify alist of UEs attached to the femto AP. As an example, the database can belocal, remote and/or distributed, and can provide a list of UEscurrently attached to the femto AP based on information, such as, butnot limited to, device ID, SIM, USIM, a mobile number, etc., associatedwith the UEs. At 1106, information received from the database can beanalyzed. In addition, data, such as, but not limited to, the receivedtraffic, PDFs, PEFs, user preferences, network provider preferences, UEparameters, femto AP parameters, can also be analyzed.

At 1108, it can be determined whether local breakout can be performed,based in part on the analysis. At 1110, the call can be routed to amacro network via a backhaul link, when determined that local breakoutcannot be performed. For example, the call can be directed to the calledparty via the macro network when determined that the called party is notattached to the femto AP. Alternately, at 1112, the call can be routedto a destination UE attached to the femto AP, when determined that localbreakout can be performed. It can be appreciated that the core networkcan be informed of the local breakout of the CS call by transmittingdata to the core network associated with the call. As an example, thedata can be utilized for billing, accounting, records, etc.

FIG. 12 illustrates a schematic wireless environment 1200 (e.g., anetwork) in which a femtocell can exploit various aspects of the subjectinnovation in accordance with the disclosed subject matter. In wirelessenvironment 1200, area 1205 can represent a coverage macro cell, whichcan be served by base station 1210. Macro coverage is generally intendedfor outdoors locations for servicing mobile wireless devices, like UE1220 _(A), and such coverage is achieved via a wireless link 1215. In anaspect, UE 1220 can be a 3GPP Universal Mobile Telecommunication System(UMTS) mobile phone.

Within macro coverage cell 1205, a femtocell 1245, served by a femtoaccess point 1230, can be deployed. A femtocell typically can cover anarea 1225 that is determined, at least in part, by transmission powerallocated to femto AP 1230, path loss, shadowing, and so forth. Coveragearea typically can be spanned by a coverage radius that ranges from 20to 50 meters. Confined coverage area 1245 is generally associated withan indoors area, or a building, which can span about 5000 sq. ft.Generally, femto AP 1230 typically can service a number (e.g., a few ormore) wireless devices (e.g., subscriber station 1220 _(B)) withinconfined coverage area 1245. In an aspect, femto AP 1230 can integrateseamlessly with substantially any PS-based and CS-based network; forinstance, femto AP 1230 can integrate into an existing 3GPP Core viaconventional interfaces like Iu-CS, Iu-PS, Gi, Gn. In another aspect,femto AP 1230 can exploit high-speed downlink packet access in order toaccomplish substantive bitrates. In yet another aspect, femto AP 1230has a LAC (location area code) and RAC (routing area code) that can bedifferent from the underlying macro network. These LAC and RAC are usedto identify subscriber station location for a variety of reasons, mostnotably to direct incoming voice and data traffic to appropriate pagingtransmitters.

As a subscriber station, e.g., UE 1220 _(A), leaves macro coverage(e.g., cell 1205) and enters femto coverage (e.g., area 1215), asillustrated in environment 1200, UE 1220 _(A) can attempt to attach tothe femto AP 1230 through transmission and reception of attachmentsignaling, effected via a FL/RL 1235; in an aspect, the attachmentsignaling can include a Location Area Update (LAU) and/or Routing AreaUpdate (RAU). Attachment attempts are a part of procedures to ensuremobility, so voice calls and sessions can continue even after amacro-to-femto transition or vice versa. It is to be noted that UE 1220can be employed seamlessly after either of the foregoing transitions.Femto networks are also designed to serve stationary or slow-movingtraffic with reduced signaling loads compared to macro networks. A femtoservice provider (e.g., an entity that commercializes, deploys, and/orutilizes femto AP 1230) therefore can be inclined to minimizeunnecessary LAU/RAU signaling activity at substantially any opportunityto do so, and through substantially any available means. It is to benoted that substantially any mitigation of unnecessary attachmentsignaling/control can be advantageous for femtocell operation.Conversely, if not successful, UE 1220 generally can be commanded(through a variety of communication means) to select another LAC/RAC orenter “emergency calls only” mode. It is to be appreciated that thisattempt and handling process can occupy significant UE battery, andfemto AP capacity and signaling resources as well.

When an attachment attempt is successful, UE 1220 can be allowed onfemtocell 1225 and incoming voice and data traffic can be paged androuted to the subscriber station through the femto AP 1230. It is to benoted also that data traffic is typically routed through a backhaulbroadband wired network backbone 1240 (e.g., optical fiber backbone,twisted-pair line, T1/E1 phone line, DSL, or coaxial cable). It is to benoted that as a femto AP 1230 generally can rely on a backhaul networkbackbone 1240 for routing and paging, and for packet communication,substantially any quality of service can handle heterogeneous packetizedtraffic. Namely, packet flows established for wireless communicationdevices (e.g., terminals 1220 _(A) and 1220 _(B)) served by femto AP1230, and for devices served through the backhaul network pipe 1240. Itis to be noted that to ensure a positive subscriber experience, orperception, it is desirable for femto AP 1230 to maintain a high levelof throughput for traffic (e.g., voice and data) utilized on a mobiledevice for one or more subscribers while in the presence of external,additional packetized, or broadband, traffic associated withapplications (e.g., web browsing, data transfer (e.g., content upload),and the like) executed in devices within the femto coverage area (e.g.,area 1225 or area 1245).

It can be appreciated that the femto AP 1230 can be substantiallysimilar to FAP 104 and include functionality, more fully describedherein, for example, with respect to systems 100-700. In particular,femto AP 1230 can include a routing component that can utilize one ormore local breakout mechanisms to facilitate efficient routing oftraffic, for example, between UE (1220 _(A) and 1220 _(B)), DH LAN 310,and/or base station 1210 via backhaul broadband wired network backbone1240

To provide further context for various aspects of the subjectspecification, FIGS. 13 and 14 illustrate, respectively, an examplewireless communication environment 1300, with associated components foroperation of a femtocell, and a block diagram of an example embodiment1400 of a femto access point, which can facilitate local breakout at afemtocell in accordance with aspects described herein.

Wireless communication environment 1300 includes two wireless networkplatforms: (i) A macro network platform 1310 that serves, or facilitatescommunication) with user equipment 1375 via a macro radio access network(RAN) 1370. It should be appreciated that in cellular wirelesstechnologies (e.g., 3GPP UMTS, HSPA, 3GPP LTE, 3GPP UMB), macro networkplatform 1310 is embodied in a Core Network. (ii) A femto networkplatform 1380, which can provide communication with UE 1375 through afemto RAN 1390 linked to the femto network platform 1380 via backhaulpipe(s) 1385, wherein backhaul pipe(s) are substantially the same abackhaul link 1240. It should be appreciated that femto network platform1380 typically offloads UE 1375 from macro network, once UE 1375attaches (e.g., through macro-to-femto handover, or via a scan ofchannel resources in idle mode) to femto RAN. It is noted that RANincludes base station(s), or access point(s), and its associatedelectronic circuitry and deployment site(s), in addition to a wirelessradio link operated in accordance with the base station(s). Accordingly,macro RAN 1370 can comprise various coverage cells like cell 1205, whilefemto RAN 1390 can comprise multiple femtocell access points. Asmentioned above, it is to be appreciated that deployment density infemto RAN 1390 is substantially higher than in macro RAN 1370.

Generally, both macro and femto network platforms 1310 and 1380 caninclude components, e.g., nodes, gateways, interfaces, servers, orplatforms, that facilitate both packet-switched (PS) andcircuit-switched (CS) traffic (e.g., voice and data) and controlgeneration for networked wireless communication. For example, macronetwork platform 1310 includes CS gateway node(s) 1312 which caninterface CS traffic received from legacy networks like telephonynetwork(s) 1340 (e.g., public switched telephone network (PSTN), orpublic land mobile network (PLMN)) or a SS7 network 1360. Moreover, CSgateway node(s) 1312 interfaces CS-based traffic and signaling andgateway node(s) 1318.

In addition to receiving and processing CS-switched traffic andsignaling, gateway node(s) 1318 can authorize and authenticate PS-baseddata sessions with served (e.g., through macro RAN) wireless devices.Data sessions can include traffic exchange with networks external to themacro network platform 1310, like wide area network(s) (WANs) 1350; itshould be appreciated that local area network(s) (LANs) can also beinterfaced with macro network platform 1310 through gateway node(s)1318. Gateway node(s) 1318 generates packet data contexts when a datasession is established. It should be further appreciated that thepacketized communication can include multiple flows that can begenerated through server(s) 1314. Macro network platform 1310 alsoincludes serving node(s) 1316 that convey the various packetized flowsof information, or data streams, received through gateway node(s) 1318.It is to be noted that server(s) 1314 can include one or more processorconfigured to confer at least in part the functionality of macro networkplatform 1310. To that end, the one or more processor can execute codeinstructions stored in memory 1330, for example.

In example wireless environment 1300, memory 1330 stores informationrelated to operation of macro network platform 1310. Information caninclude business data associated with subscribers; market plans andstrategies, e.g., promotional campaigns, business partnerships;operational data for mobile devices served through macro networkplatform; service and privacy policies; end-user service logs for lawenforcement; and so forth. Memory 1330 can also store information fromat least one of telephony network(s) 1340, WAN(s) 1350, or SS7 network1360.

Femto gateway node(s) 1384 have substantially the same functionality asPS gateway node(s) 1318. Additionally, femto gateway node(s) 1384 canalso include substantially all functionality of serving node(s) 1316. Inan aspect, femto gateway node(s) 1384 facilitates handover resolution,e.g., assessment and execution. Server(s) 1382 have substantially thesame functionality as described in connection with server(s) 1314 andcan include one or more processor configured to confer at least in partthe functionality of macro network platform 1310. To that end, the oneor more processor can execute code instructions stored in memory 1386,for example.

Memory 1386 can include information relevant to operation of the variouscomponents of femto network platform 1380. For example operationalinformation that can be stored in memory 1386 can comprise, but is notlimited to, subscriber information; contracted services; maintenance andservice records; femtocell configuration (e.g., devices served throughfemto RAN 1390; access control lists, or white lists); service policiesand specifications; privacy policies; add-on features; and so forth

With respect to FIG. 14, in example embodiment 1400, femtocell AP 1410can receive and transmit signal(s) (e.g., traffic and control signals)from and to wireless devices, access terminals, wireless ports androuters, etc., through a set of antennas 1469 ₁-1469 _(N). It should beappreciated that while antennas 1469 ₁-1469 _(N) are a part ofcommunication platform 1425, which comprises electronic components andassociated circuitry that provides for processing and manipulating ofreceived signal(s) (e.g., a packet flow) and signal(s) (e.g., abroadcast control channel) to be transmitted. In an aspect,communication platform 1425 includes a transmitter/receiver (e.g., atransceiver) 1466 that can convert signal(s) from analog format todigital format upon reception, and from digital format to analog formatupon transmission. In addition, receiver/transmitter 1466 can divide asingle data stream into multiple, parallel data streams, or perform thereciprocal operation. Coupled to transceiver 1466 is amultiplexer/demultiplexer 1467 that facilitates manipulation of signalin time and frequency space. Electronic component 1467 can multiplexinformation (data/traffic and control/signaling) according to variousmultiplexing schemes such as time division multiplexing (TDM), frequencydivision multiplexing (FDM), orthogonal frequency division multiplexing(OFDM), code division multiplexing (CDM), space division multiplexing(SDM). In addition, mux/demux component 1467 can scramble and spreadinformation (e.g., codes) according to substantially any code known inthe art; e.g., Hadamard-Walsh codes, Baker codes, Kasami codes,polyphase codes, and so on. A modulator/demodulator 1468 is also a partof operational group 1425, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like.

Femto access point 1410 also includes a processor 1445 configured toconfer functionality, at least partially, to substantially anyelectronic component in the femto access point 1410, in accordance withaspects of the subject innovation. In particular, processor 1445 canfacilitate femto AP 1410 to implement configuration instructionsreceived through communication platform 1425, which can include storingdata in memory 1455. In addition, processor 1445 facilitates femto AP1410 to process data (e.g., symbols, bits, or chips) formultiplexing/demultiplexing, such as effecting direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, etc. Moreover, processor 1445 canmanipulate antennas 1469 ₁-1469 _(N) to facilitate beamforming orselective radiation pattern formation, which can benefit specificlocations (e.g., basement, home office . . . ), covered by femto AP; andexploit substantially any other advantages associated with smart-antennatechnology. Memory 1455 can store data structures, code instructions,system or device information like device identification codes (e.g.,IMEI, MSISDN, serial number . . . ) and specification such as multimodecapabilities; code sequences for scrambling; spreading and pilottransmission, floor plan configuration, access point deployment andfrequency plans; and so on. Moreover, memory 1455 can storeconfiguration information such as schedules and policies; femto APaddress(es) or geographical indicator(s); access lists (e.g., whitelists); license(s) for utilization of add-features for femto AP 1410,and so forth.

In embodiment 1400, processor 1445 is coupled to the memory 1455 inorder to store and retrieve information necessary to operate and/orconfer functionality to communication platform 1425, broadband networkinterface 1335 (e.g., a broadband modem), and other operationalcomponents (e.g., multimode chipset(s), power supply sources . . . ; notshown) that support femto access point 1410. The femto AP 1410 canfurther include a routing component 108, management component 308,security component 316, UE DH agent 608, femto DH agent 614, which caninclude functionality, as more fully described herein, for example, withregard to systems 100-700. In addition, it is to be noted that thevarious aspects disclosed in the subject specification can also beimplemented through (i) program modules stored in a computer-readablestorage medium or memory (e.g., memory 1386 or memory 1455) and executedby a processor (e.g., processor 1445), or (ii) other combination(s) ofhardware and software, or hardware and firmware.

Referring now to FIG. 15, there is illustrated a block diagram of a UE1500 suitable for communication with a DH LAN via a femto network inaccordance with the innovation. The UE 1500 can include a processor 1502for controlling all onboard operations and processes. A memory 1504 caninterface to the processor 1502 for storage of data and one or moreapplications 1506 being executed by the processor 1502. A communicationscomponent 1508 can interface to the processor 1502 to facilitatewired/wireless communication with external systems (e.g., femtocell andmacro cell). The communications component 1508 interfaces to a locationcomponent 1509 (e.g., GPS transceiver) that can facilitate locationdetection of the UE 1500. Note that the location component 1509 can alsobe included as part of the communications component 1508.

The UE 1500 can include a display 1510 for displaying content downloadedand/or for displaying text information related to operating and usingthe device features. A serial I/O interface 1512 is provided incommunication with the processor 1502 to facilitate serial communication(e.g., USB, and/or IEEE 1394) via a hardwire connection. Audiocapabilities are provided with an audio I/O component 1514, which caninclude a speaker for the output of audio signals related to, forexample, recorded data or telephony voice data, and a microphone forinputting voice signals for recording and/or telephone conversations.

The device 1500 can include a slot interface 1516 for accommodating asubscriber identity module (SIM) 1518. Firmware 1520 is also provided tostore and provide to the processor 1502 startup and operational data.The UE 1500 can also include an image capture component 1522 such as acamera and/or a video decoder 1524 for decoding encoded multimediacontent. The UE 1500 can also include a power source 1526 in the form ofbatteries, which power source 1526 interfaces to an external powersystem or charging equipment via a power I/O component 1528. Inaddition, the UE 1500 can include a DH client 612 that facilitatescommunication between UE 1500 and home network via a femto AP. The DHclient 612 can include functionality, as more fully described herein,for example, with regard to system 600.

Referring now to FIG. 16, there is illustrated a block diagram of acomputer operable to execute the disclosed communication architecture.In order to provide additional context for various aspects of thesubject specification, FIG. 16 and the following discussion are intendedto provide a brief, general description of a suitable computingenvironment 1600 in which the various aspects of the specification canbe implemented. While the specification has been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that thespecification also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disk (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 16, the example environment 1600 forimplementing various aspects of the specification includes a computer1602, the computer 1602 including a processing unit 1604, a systemmemory 1606 and a system bus 1608. The system bus 1608 couples systemcomponents including, but not limited to, the system memory 1606 to theprocessing unit 1604. The processing unit 1604 can be any of variouscommercially available processors. Dual microprocessors and othermulti-processor architectures can also be employed as the processingunit 1604.

The system bus 1608 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1606includes read-only memory (ROM) 1610 and random access memory (RAM)1612. A basic input/output system (BIOS) is stored in a non-volatilememory 1610 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1602, such as during start-up. The RAM 1612 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1602 further includes an internal hard disk drive (HDD)1614 (e.g., EIDE, SATA), which internal hard disk drive 1614 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1616, (e.g., to read from or write to aremovable diskette 1618) and an optical disk drive 1620, (e.g., readinga CD-ROM disk 1622 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1614, magnetic diskdrive 1616 and optical disk drive 1620 can be connected to the systembus 1608 by a hard disk drive interface 1624, a magnetic disk driveinterface 1626 and an optical drive interface 1628, respectively. Theinterface 1624 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject specification.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1602, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the example operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the specification.

A number of program modules can be stored in the drives and RAM 1612,including an operating system 1630, one or more application programs1632, other program modules 1634 and program data 1636. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1612. It is appreciated that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1602 throughone or more wired/wireless input devices, e.g., a keyboard 1638 and apointing device, such as a mouse 1640. Other input devices (not shown)can include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1604 through an input deviceinterface 1642 that is coupled to the system bus 1608, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1644 or other type of display device is also connected to thesystem bus 1608 via an interface, such as a video adapter 1646. Inaddition to the monitor 1644, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1602 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1648. The remotecomputer(s) 1648 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1602, although, for purposes of brevity, only a memory/storage device1650 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1652 and/orlarger networks, e.g., a wide area network (WAN) 1654. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1602 isconnected to the local network 1652 through a wired and/or wirelesscommunication network interface or adapter 1656. The adapter 1656 canfacilitate wired or wireless communication to the LAN 1652, which canalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1656.

When used in a WAN networking environment, the computer 1602 can includea modem 1658, or is connected to a communications server on the WAN1654, or has other means for establishing communications over the WAN1654, such as by way of the Internet. The modem 1658, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1608 via the serial port interface 1642. In a networkedenvironment, program modules depicted relative to the computer 1602, orportions thereof, can be stored in the remote memory/storage device1650. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

The computer 1602 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, orwith products that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” and substantially any other information storage componentrelevant to operation and functionality of a component, refer to “memorycomponents,” or entities embodied in a “memory” or components comprisingthe memory. It will be appreciated that the memory components, orcomputer-readable storage media, described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

What has been described above includes examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “includes” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

1. (canceled)
 2. A femto access point device, comprising: a processor;and a memory that stores executable instructions that, when executed bythe processor, facilitate performance of operations, comprising:determining routing data that represents a first route via whichcommunication data, received from a user equipment that is coupled tothe femto access point device, is to be routed, wherein the first routecomprises a first path from the femto access point device to a networkdevice of a wide area network via a local area network device coupled tothe femto access point device, and in response to receiving instructiondata indicative of an instruction to override a local breakout,disabling local breakout functionality performed via the femto accesspoint device to update the routing data to represent a second route viawhich the communication data is to be routed, wherein the second routecomprises a second path from the femto access point device to thenetwork device via a macro network device coupled to the femto accesspoint device.
 3. The femto access point device of claim 2, wherein theoperations further comprise: analyzing the communication data tofacilitate the determining of the routing data.
 4. The femto accesspoint device of claim 2, wherein the determining the routing datacomprises determining the routing data based on network congestion dataassociated with the macro network device.
 5. The femto access pointdevice of claim 2, wherein the determining the routing data comprisesdetermining the routing data based on timing data indicative of aresponse time period associated with a transfer of the communicationdata from the user equipment to the network device.
 6. The femto accesspoint device of claim 2, wherein the operations further comprise:receiving, via the macro network device, policy data associated with adefined routing policy, wherein the determining the routing datacomprises determining the routing data based on the policy data.
 7. Thefemto access point device of claim 6, wherein the receiving the policydata comprises receiving the policy data subsequent to an authorizationof the femto access point device with the macro network device.
 8. Thefemto access point device of claim 6, wherein the receiving the policydata comprises receiving the policy data during an initializationprocedure employed to activate the femto access point device.
 9. Thefemto access point device of claim 2, wherein the receiving theinstruction data comprises receiving timing data indicative of a time atwhich the disabling is to be initiated.
 10. The femto access pointdevice of claim 2, wherein the receiving the instruction data comprisesreceiving the instruction data in response to determining that requestdata indicative of a request is received from a security device.
 11. Thefemto access point device of claim 2, wherein the operations furthercomprise: based on the routing data, directing the communication data tothe network device.
 12. The femto access point device of claim 2,wherein the determining the routing data comprises determining therouting data based on destination address data indicative of the networkdevice.
 13. A method, comprising: determining, by a femto access pointdevice comprising a processor, routing data that represents a firstroute via which communication data, received from a user equipment thatis coupled to the femto access point device, is to be routed, whereinthe first route comprises a first path from the femto access pointdevice to a network device of a wide area network via a local areanetwork device coupled to the femto access point device; and in responseto receiving instruction data indicative of an instruction to override alocal breakout, disabling, by the femto access point device, localbreakout functionality performed via the femto access point device tofacilitate a transmission of the communication data to the networkdevice via a second route that comprises a second path from the femtoaccess point device to the network device via a macro network devicecoupled to the femto access point device.
 14. The method of claim 13,wherein the determining the routing data comprises determining therouting data based on network congestion data associated with the macronetwork device.
 15. The method of claim 13, wherein the determining therouting data comprises determining the routing data based on timing dataindicative of a response time period associated with a transfer of thecommunication data from the user equipment to the network device. 16.The method of claim 13, wherein the determining the routing datacomprises determining the routing data based on analyzing header dataassociated with the communication data.
 17. The method of claim 13,wherein the determining the routing data comprises determining therouting data based on policy data received via the macro network device.18. The method of claim 17, further comprising: receiving, by the femtoaccess point device, the policy data during an initialization procedureemployed to activate the femto access point device.
 19. Acomputer-readable storage device comprising executable instructionsthat, in response to execution, cause a femto access point devicecomprising a processor to perform operations, comprising: receiving,from a user equipment that is coupled to the femto access point device,communication data that is directed to a network device of a wide areanetwork; determining that a local breakout functionality is to beperformed, wherein the local breakout functionality initiates routing ofthe communication data by employing a first route from the femto accesspoint device to the network device via a local area network devicecoupled to the femto access point device; and in response to receivinginstruction data indicative of an instruction to override a localbreakout, disabling, by the femto access point device, the localbreakout functionality to initiate a transmission of the communicationdata to the network device by employing a second route from the femtoaccess point device to the network device via a macro network devicecoupled to the femto access point device.
 20. The computer-readablestorage device of claim 19, wherein the determining comprisesdetermining that local breakout functionality is to be performed basedon network congestion data associated with the macro network device. 21.The computer-readable storage device of claim 19, wherein thedetermining comprises determining that local breakout functionality isto be performed based on timing data indicative of a response timeperiod associated with a transfer of the communication data from theuser equipment to the network device.